fix: complete classic manager compatibility paths - #838

This is not merge-ready against current master. The branch now conflicts in the control path, and master has since landed substantial classic window/menu behavior plus shared cross-architecture runtime and memory changes that overlap the nine-subsystem scope here.

Please rebase onto current master and reduce the PR to the compatibility work that is still missing after those releases. If the remaining delta is still broad, split it into focused issue/PR units so each documented Toolbox behavior can be reviewed and released independently. Then rerun the focused trap tests, full suite, wasm check, deterministic route, and BasiliskII comparison. I am leaving #770 open and not merging the stale conflict resolution.

I attempted a rebase onto current master in an isolated checkout. This is not a mechanical realignment: it conflicts in globals, runner, controls, dispatcher and menus. In particular, the incoming runner code restores ActiveInterruptCallback/active_interrupt_callback-era scheduling while current master uses the shared guest-call machinery and callback_suspends_guest_clock; the MENU changes also overlap current complete-resource and nested-MDEF handling. Taking either side wholesale would lose behavior. Please port only the still-missing notification/control behaviors to the current task model and remove superseded menu changes, with focused regressions and a fresh #770 route/oracle comparison. I left the public branch unchanged and the PR open.